feat(basic-auth): auth - #2

Top hotspots

Top directories

ECC Tools uses this to decide whether recommendations should stay at commit-history/setup guidance or expand into CI, security, harness, reference-set, AI-routing, and team backlog work.

• Schema or model changes may ship without migration follow-up: The PR changes schema or model-facing files but does not include any obvious migration artifact.
• CLI changes may ship without shell or end-to-end coverage: The PR changes CLI, bin, or command-entry files without touching any obvious CLI-focused integration or end-to-end tests.
• CI workflow changes may ship without failure-mode evidence: The PR changes CI workflows or test-runner entrypoints without touching CI failure fixtures, captured logs, troubleshooting notes, or regression evidence.
• Dependency or CI drift could surface after merge: Package or workflow changes landed without an accompanying lockfile update, which often turns into CI or release noise later.

• db: add migration follow-up for apps/Backend/src/flycatch_api/models/init.py + apps/Backend/src/flycatch_api/models/admin_session.py: Backfill the missing migration artifact before another schema or model change lands on top.
• test: add CLI coverage for apps/Backend/src/flycatch_api/cli/bootstrap.py + apps/Backend/src/flycatch_api/cli/provision_admin.py: Backfill CLI coverage before another command-surface change lands on the touched paths.
• ci: add failure-mode evidence for .github/workflows/quality-gates.yml + scripts/check-secrets.mjs: Backfill CI failure-mode evidence before another workflow or test-runner change lands on the touched surface.
• chore: refresh lockfile and validate CI after dependency updates: Package or workflow changes without a lockfile refresh tend to turn into noisy follow-up fixes after merge.

Copy-ready bodies

db: add migration follow-up for apps/Backend/src/flycatch_api/models/init.py + apps/Backend/src/flycatch_api/models/admin_session.py

## Summary
- Add the missing migration or schema rollout step for the recently changed schema surface.

## Why
- Backfill the missing migration artifact before another schema or model change lands on top.

## Touched paths
- `apps/Backend/src/flycatch_api/models/__init__.py`
- `apps/Backend/src/flycatch_api/models/admin_session.py`

## Validation
- Create the migration or schema rollout artifact used by this repo.
- Run the repo migration / schema validation flow and verify the changed models still match production expectations.

test: add CLI coverage for apps/Backend/src/flycatch_api/cli/bootstrap.py + apps/Backend/src/flycatch_api/cli/provision_admin.py

## Summary
- Add shell, CLI, or end-to-end coverage for the recently changed command surface.

## Why
- Backfill CLI coverage before another command-surface change lands on the touched paths.

## Touched paths
- `apps/Backend/src/flycatch_api/cli/bootstrap.py`
- `apps/Backend/src/flycatch_api/cli/provision_admin.py`

## Validation
- Add or extend shell, CLI, or end-to-end coverage for the changed command surface.
- Exercise the user-facing command invocation and expected exit/output behavior.

ci: add failure-mode evidence for .github/workflows/quality-gates.yml + scripts/check-secrets.mjs

## Summary
- Add CI failure-mode evidence for the recently changed workflow or test-runner surface.

## Why
- Backfill CI failure-mode evidence before another workflow or test-runner change lands on the touched surface.

## Touched paths
- `.github/workflows/quality-gates.yml`
- `scripts/check-secrets.mjs`

## Validation
- Add or update a CI failure fixture, captured failing log, troubleshooting note, workflow dry-run evidence, or regression test for the changed CI/test-runner behavior.
- Run the affected workflow or test-runner entrypoint locally or in CI and record pass/fail evidence.

chore: refresh lockfile and validate CI after dependency updates

## Summary
- Refresh the lockfile and rerun CI after the dependency or workflow changes in this PR.

## Why
- Package or workflow changes without a lockfile refresh tend to turn into noisy follow-up fixes after merge.

## Touched paths
- `.github/workflows/quality-gates.yml`

## Validation
- Refresh the lockfile in the same package manager used by the repo.
- Run the repo typecheck / test / CI entrypoints that depend on the updated package graph.

After merging, import with:

/instinct-import .claude/homunculus/instincts/inherited/flycatch-website-instincts.yaml